Three rules hold this together, and the first is what makes it affordable.

**Nothing animated changes layout.** Every animation here interpolates a colour.
A frame in flight never re-measures a row, never reflows the mod list and never
touches the file tree - which matters, because a fully expanded Skyrim Data tree
is six figures of rows and re-laying it out sixty times a second would be a
stutter, not a flourish. Turning motion off therefore changes no spacing at all.

**The clock only runs while something is moving.** `anim::animating` gates the
frame subscription, so an idle window subscribes to no timer. The cost at rest
is not small, it is zero - the same condition the drag-scroll, hover-expand and
run-poll timers already use.

**A phase ends by itself.** `Phase` holds the instant a transition began and
derives everything from elapsed time, so nothing has to remember to switch it
off, and a missed frame shows up as a jump forward rather than as an animation
stuck half way.

## What moves

The two tab strips cross-fade. Both ends of the blend come from iced's own
`button::primary` and `button::secondary`, evaluated against the live theme, so
no colour is named and the transition stays right on the dark palette and on any
palette added later. The tab being LEFT runs the same transition backwards -
without that the arriving tab fades in while the old one snaps, which reads as a
glitch rather than as a transition.

A new status message fades in, so a status that replaces another is visibly a
new one rather than a word that quietly became a different word. It is armed by
comparing `status` after each message rather than at the dozen places across
`state.rs` that assign it: "remember to also start the fade" is a rule that
would be forgotten by the second one.

## Motion is a setting, because it has to be

`motion` in `settings.ini`, on unless explicitly off, with the toggle under
Preferences -> Appearance. Off means every animated value is drawn at its
destination on the first frame - not a quicker animation, none - and the frame
timer is never subscribed. The Colony convention requires that a program which
animates can be told not to; this is that.

`AnimationTick` is ambient. It fires sixty times a second, so treating it as an
action would not merely shorten an armed two-click confirmation's life, it would
end it between the two clicks every time - the defect the pointer and the
download tick already taught this window, at sixty times the rate. It joins the
set assertion that exists to catch the next timer somebody adds.

273 GUI tests, 138 elsewhere, clippy clean on the pinned 1.94.1.

Measured against `design/settings-page.md` in Project-Colony-Resources, this
page broke the convention's first structural rule and was missing one of its
three mandatory categories.

## It was a modal, which is the one thing it must not be

The convention names a modal, a separate window and a popover as the three
counter-examples, and this was the first. It is a page now: it replaces the
content area, and the header, menu bar, toolbar and status bar all stay exactly
where they are - the program's chrome does not move because the user went to
configure it.

What that buys is not tidiness. The card was capped at 620x240, so every
category was read through a 240-pixel slot however large the window was. The
screen that most needs room to be scanned had the least of it.

## Accessibility was missing, and it is not optional

"The Accessibility category is part of the skeleton, not a nice-to-have." The
first three categories are imposed and ordered - General, Appearance,
Accessibility - and this had five with the third absent.

Motion moves there from Appearance, where the previous commit had put it. The
distinction is not filing: Appearance is what the window looks like,
Accessibility is what it does for somebody who needs it to do less.

The convention also asks for a high-contrast palette, a dyslexia-friendly font
and a text scale. Eidos has none of the three - every size in this window is a
literal, so a scale is a change to the whole GUI rather than a setting. The
category says so in as many words rather than showing switches that do nothing.

## The rest of the checklist

- Titled **Preferences**, at 22, not "Settings" at 18. The convention settles the
  user-facing word; only the code is still named `settings_*`, which costs the
  user nothing.
- `settings_dialog` is now `preferences_page`: a function whose name disagrees
  with what it returns is how the next reader is misled.
- Each category opens with its own heading and one line saying what it changes.
  General's carries the contract that matters most: preferences are saved
  automatically. There is no Save button and there must not be one.
- Close at 13, padding [6, 14]; rail buttons at [8, 14], widened to 148 so
  "Accessibility" does not resize the column.
- Descriptions in a muted ink, so a category reads as titles with explanations
  rather than as two columns of equally loud text.

## Two deliberate deviations, both about scale

The convention's chevrons are Nerd Font codepoints. Eidos bundles no Nerd Font -
it uses PNG icons - so those would render as tofu; the existing triangles stay.

Section titles are 14, not the convention's 15. That number assumes Colony's
type scale, whose body text is 13 where Eidos's is 12, and 15 would leave a
section title as loud as the category heading above it. What the convention
specifies is the hierarchy - page, category, section, body - and this keeps it,
at 22 / 16 / 14 / 12.

Six new tests state the convention where a refactor would otherwise break it
silently: the first three categories and their order, About last, every category
explaining itself in words it does not repeat, General carrying the no-Save
contract, and motion filed under Accessibility. The rank table is an exhaustive
match, so adding a category without placing it does not compile.

278 GUI tests, clippy clean on the pinned 1.94.1.